General Considerations and Limitations

This section describes known limitations.

This section covers the following topics:

• If all logical disks are degraded, the events might be out of order
• The health monitor and front panel are not supported
• AutoSupport and SNMP filters might hide lower severity events
• Startup takes too long
• If an AutoSupport e-mail fails, there is no cause provided
• When the head or compact flash are replaced, the port assignment information needs to be reapplied
• The web is unresponsive during disk import
• Automatic RAID group repair might start sooner expected
• Events and actions about parallel SCSI devices display do not display addresses
• If over allocation is turned on, and the RAID groups become full, the remaining volumes report an error as soon as they are loaded
• A new HPUX Data Protector might not be discovered immediately after a VTL reboot

If all RAID groups are degraded, the events might be out of order

If more than one RAID group is degraded, events describing the RAID group status, including rebuilds, might appear out of order in the event log.

Bug ID 181257

The health monitor and front panel are not supported

The current release does not support the NetApp NearStore VTL front panel, and does not support the NetApp health monitor. Both will be supported in a future release.

Bug ID 181261

AutoSupport and SNMP filters might hide lower severity events

Event filters are used to reduce superfluous AutoSupport and SNMP event e-mails. Under some cirmcumstances, these filters might hide lower severity, but valid events.

Startup takes too long

During startup, all interfaces are checked for connectivity. Unconnected interfaces must time out and this can result in a slow startup.

Bug ID 188564

If an AutoSupport e-mail fails, there is no cause provided

If an AutoSupport e-mail is not sent, the event message provides no cause and there are no user diagnostics to determine the cause of the failure,

Bug ID 188570

When the head or compact flash is replaced, the port assignment information needs to be reapplied

When saved configuration data is used to build a NearStore VTL system, for example after replacing the head or replacing the compact flash, the restored configuration does not set the port assignments correctly. You must reenter the port assignments.

Bug ID 188571

Unresponsive GUI during disk import

When disk import starts up during a system rebuild, the graphical user interface becomes unresponsive for a period of time, after which the system again becomes responsive.

Bug ID 188572

Automatic RAID group repair might start sooner than expected

The repair task timer is not reset after a RAID group is rebuilt, so if a RAID group is degraded shortly afer being rebuilt, a new rebuild starts before the usual 10 minute delay. This has no adverse effects.

Bug ID 188573

Events and actions about parallel SCSI devices do not display addresses

The physical tape device page only provides a port column, but for
parallel SCSI devices, the page should provde the SCSI address.

Bug ID 188575

If overallocation is turned on, and the RAID groups become full, the remaining volumes report an error as soon as they are loaded

If overallocation is turned on, backup applications can be confused about the number of available virtual tapes, resulting in media errors and failed backups.

Bug ID 188576

A new HPUX Data Protector might not be discovered immediately after a VTL reboot

After a an HP-UX Data Protector is first connected to a NearStore VTL system and the VTL system is rebooted, auto-discovery might not associate the tape drives with the the changer. A work around is to manually trigger an auto-discovery.

Bug ID 188577